Skip to main content

Install Fluent RESTful Engine Container in an Azure App Service

This article describes how to deploy a Java RESTful Engine to Azure App Service. This is the prefered method for deploying the RESTful engine in an Azure App Service.

Creating the Azure App Service​

When Creating your Azure App Service, make sure you set the following settings:

  • On The Basics Tab:

    • Publish: Container
    • Operating System: Linux
    • Java Web Server Stack: Tomcat 10.0

  • On The Container Tab:

note

Where {VERSION} is the version of the Java RESTful engine you wish to use. All available versions can be seen by browsing here, then choosing the "Image tags" tab. You may also just type latest if you wish to just use the latest engine version instead of a specific version.***

Creating Storage Account​

  • Create a storage account with any settings as long as it will be available from your App Service

Configuration​

  • Setting your license key and applying other configuration settings
    • On the Environment Variables blade set license to your license key (you can skip this if you're providing your license key in your POST request to the engine)
    • You may apply any other Fluent configuration values that would normally go into WindwardReports.properties in this same way.
    • Choose "Save"
  • Persisting your App Data Directory
    • On the storage account your created earlier create a new "File Share" with any settings
    • Wait for your file share to be created
    • Back on our App service on the Configuration blade choose "Path mappings"
    • Choose "New Azure Storage Mount"
    • Name it whatever you want
    • Choose "Basic"
    • Choose your storage account
    • For "Storage Type" select "Azure Files"
    • Set "Protocol" to "SMB" (default)
    • Set "Mount Path" to /usr/local/tomcat/webapps/App_Data
    • Choose "Save"
danger

We had issues getting the container image to boot up when using the non production level tiers of the App Service Plan